Enhanced security for visually impaired users of touchscreen interfaces using false entry notifications for user input

ABSTRACT

The technology disclosed herein enhances security for visually impaired users by presenting haptic notifications to indicate certain input notifications are false. In a particular embodiment, a method includes presenting, from a user system, graphical input elements and presenting a haptic notification. The haptic notification indicates that the next input received after presenting the haptic notification will not be entered by the user system. In response to receiving input of a first input element of the graphical input elements immediately following the haptic notification, the method includes presenting a non-haptic notification. The non-haptic notification falsely indicates the input has been entered.

TECHNICAL BACKGROUND

Visually impaired users often rely on assistive software features andalternative user interfaces to operate user systems having touchscreens.Such user systems include the vast majority of smartphones and tabletcomputers currently produced. Many assistive features (e.g., TalkBackfor Android™ devices and VoiceOver for Apple® devices) will direct theuser system to synthesize speech audibly describing elements beingdisplayed on a touchscreen. If one of the elements is an element foraccepting user input (e.g., a button, icon, link, soft-key, etc.), thenthe user may perform a prescribed action (e.g., double tap the screen)after that element is described to enter the input associated with thatelement. When the user is entering sensitive information (e.g.,passcodes, bank information, etc.) in this manner, users nearby may beable to hear the information read aloud by the assistive feature.Privacy for the visually impaired user is, therefore, compromisedrelative to a sighted user that does not require audible descriptionsfrom the assistive feature.

SUMMARY

The technology disclosed herein enhances security for visually impairedusers by presenting haptic notifications to indicate certain inputnotifications are false. In a particular embodiment, a method includespresenting, from a user system, graphical input elements and presentinga haptic notification. The haptic notification indicates that the nextinput received after presenting the haptic notification will not beentered by the user system. In response to receiving input of a firstinput element of the graphical input elements immediately following thehaptic notification, the method includes presenting a non-hapticnotification. The non-haptic notification falsely indicates the inputhas been entered.

In some examples, the method includes receiving second input of one ofthe graphical input elements and entering the second input into the usersystem. In those examples, the method may include presenting a secondnon-haptic notification indicating the second input is entered. Also, inthose examples, before receiving the second input, the method mayinclude presenting a second haptic notification that is different fromthe haptic notification. The second haptic notification indicates thatthe next input received after presenting the second haptic notificationwill be entered by the user system and the second input is receivedimmediately following the second haptic notification. Further, in thoseexamples, after receiving the second input, the method may includepresenting a second haptic notification that is different from thehaptic notification. The second haptic notification in this caseindicating the second input is entered.

In some examples, the non-haptic notification includes an audiblenotification.

In some examples, presenting the graphical input elements includespresenting an audible description of the first input element immediatelybefore receiving the input.

In some examples, the non-haptic notification includes a visualindication that the input has been entered.

In some examples, the graphical input elements represent characters forentering a passcode.

In some examples, the method includes receiving an instruction from auser of the user system activating a privacy feature of the user system,wherein the privacy feature triggers use of the haptic notification.

In another example, an apparatus is provides having one or more computerreadable storage media and a processing system operatively coupled withthe one or more computer readable storage media. Program instructionsstored on the one or more computer readable storage media, when read andexecuted by the processing system, direct the apparatus to presentgraphical input elements and present a haptic notification. The hapticnotification indicates that the next input received after presenting thehaptic notification will not be entered by the user system. In responseto receiving input of a first input element of the graphical inputelements immediately following the haptic notification, the programinstructions direct the processing system to present a non-hapticnotification. The non-haptic notification falsely indicates the inputhas been entered.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an implementation for haptically notifying a userthat certain input notifications are false.

FIG. 2 illustrates an operation to haptically notify a user that certaininput notifications are false.

FIG. 3 illustrates an operational scenario for haptically notifying auser that certain input notifications are false.

FIG. 4 illustrates an operational scenario for haptically notifying auser that certain input notifications are false.

FIG. 5 illustrates an operational scenario for haptically notifying auser that certain input notifications are false.

FIG. 6 illustrates a graphical display of a user system for hapticallynotifying a user that certain input notifications are false.

FIG. 7 illustrates a graphical display of a user system for hapticallynotifying a user that certain input notifications are false.

FIG. 8 illustrates a computing architecture for haptically notifying auser that certain input notifications are false.

DETAILED DESCRIPTION

The user system described herein presents haptic notifications thatindicate to the device's user that certain inputs will not be enteredeven though a different notification falsely indicates that the inputhas been entered. Specifically, a haptic notification is presentedindicating that the next input received into the user system will not beentered. After receiving the next input from the user, the user systempresents a notification that the input has been entered (e.g., speakingout that the input has been entered and/or displaying the input in anentry field displayed by the user system). However, in accordance withthe haptic notification, that input is not actually entered. As such, aperson eavesdropping on the user's input into the system may erroneouslyconclude from the notification that the input has been entered. Thatperson, being unable to feel the haptic notifications of the usersystem, will be unaware that they are not receiving the actualinformation being input by the user.

FIG. 1 illustrates implementation 100 for haptically notifying a userthat certain input notifications are false. Implementation 100 includesuser system 101, which is operated by user 141 in this example. Usersystem 101 includes haptic device 121, speaker 122, and display 123.Display 123 may include a Liquid Crystal Display (LCD), Light EmittingDiode (LED) display, Organic LED, or any other type of visual displaymechanism. Display 123 is a touchscreen and further includes circuitryand other components to detect a user's touch. Two common types oftouchscreens are capacitive and resistive, although alternative touchsensing mechanisms may be used. Speaker 122 may include a magnet, voicecoil, diaphragm, or any other type of component for producing sound.Haptic device 121 may include one or more solenoids, motors, electrodes,and/or some other type of component that can be felt by the user whenactivated. For example, haptic device 121 may include a vibration motorthat, when activated, vibrates user system 101. When user 141 is incontact with user 141 (e.g., being held by user 141), user 141 can feelthe vibration created by the activation of haptic device 121. In otherexamples, haptic device 121 may be a peripheral worn by user 141, orotherwise in contact with user 141's body, and in communication withuser system 101 to control activation of haptic device 121.

FIG. 2 illustrates operation 200 to haptically notify a user thatcertain input notifications are false. In operation 200, user system 101presents graphical input elements 113 to user 141 (201). Graphical inputelements 113 may be any type of graphic displayed by user system 101through which user 141 provides input to user system 101. Graphicalinput elements 113 may include graphical icons, buttons, links, or someother type of user-selectable graphic. Graphical input elements 113 mayinclude keys of a displayed dial-pad or keyboard (e.g., each letter ofthe alphabet may be represented by a different one of graphical inputelements 113). User system 101 may present graphical input elements 113visually and/or audibly. Audible presentation of graphical inputelements 113 may include user system 101 presenting element descriptions131 from speaker 122 so as even a visually impaired user will understandgraphical input elements 113. User system 101 may present elementdescriptions 131 for all of graphical input elements 113 automaticallyor may present respective ones of element descriptions 131 in responseto actions taken by user 141. For example, user 141 may move theirfinger on display 123 and, when the finger is on a particular one ofgraphical input elements 113, user system 101 presents a description ofthat graphical input element (e.g., when on the letter ‘R’ of akeyboard, user system 101 may synthesize speech saying “R” or “Theletter R”). When the finger moves to another graphical input element, adescription of that element is presented. In some examples, operation200 may be of benefit to non-visually impaired users and elementdescriptions 131 may not be necessary as the user can see graphicalinput elements 113 on display 123. Alternatively, if a visually impaireduser cannot see display 123 anyway, then graphical input elements 113may not actually be displayed (e.g., to save battery power). As such,element descriptions 131 describe what would be displayed (i.e.,graphical input elements 113) and user touches on display 123 would bemapped to where graphical input elements 113 would be displayed ifdisplay 123 was actually displaying those elements. Similarly, ratherthan displaying nothing, user system 101 may display something otherthan graphical input elements 113 as a decoy display presentation todeceive a person looking at display 123. For example, display 123 maydisplay a representation of a music player application as a decoy togive other people the impression that user 141 is managing their musiclibrary rather than interactive with graphical display elements 113. Insuch examples, element descriptions 131 are presented to describegraphical input elements 113, which would be displayed had the decoydisplay not been presented, and user touches on display 123 would bemapped to where graphical input elements 113 would be displayed ifdisplay 123 was actually displaying those elements.

User system 101 presents haptic notification 132 to indicate that thenext input received after presenting haptic notification 132 will not beentered by user system 101 (202). Haptic notification 132 may be anytype of haptic output by haptic device 121. Different types of hapticnotifications from user system 101 (e.g., vibration patterns, tappatterns, etc.) may correspond to different information being conveyed.For example, one vibration pattern (e.g., two short vibrations) may beused for haptic notification 132 to convey to user 141 that the nextinput will not be entered while another vibration pattern (e.g., onelong followed by one short vibration) may be used to convey that amessage has been received. In some examples, haptic notification 132 maynot be unique with respect to other haptic notifications but the contextof graphical input elements 113 in association with haptic notification132 enables user 141 to recognize that haptic notification 132 is meantto convey the next input will not be entered.

User system 101 receives input of one of graphical input elements 113immediately following haptic notification 132 (203). User 141 mayprovide the input by simply selecting the graphical input element (e.g.,tapping on display 123 where the element is displayed) or may providethe input in some other prescribed manner. For example, user system 101may be executing an assistive feature for visually impaired users thatalso handles element descriptions 131. When the graphical input elementis spoken in element descriptions 131, the assistive feature mayindicate that user 141 can tap, or double tap, anywhere on the screen toinput the element that was just spoken. User 141, therefore, does notneed to see exactly where the desired graphical input element isdisplayed to select it. Regardless of how the input is received, theinput is immediate in the sense that the input is received with nointervening input from when haptic notification 132 was presented.Otherwise, that intervening input would have been the next receivedinput from user 141.

In response to receiving the input, user 141 presents a non-hapticnotification falsely indicating the input has been entered (204). Thenon-haptic notification is a false indication of input entry because theinput is not actually input for the purposes user 141 is purportedlydoing so, as haptic notification 132 previously indicated. For instance,if user 141 is entering a bank account number, user system 101 the inputis not considered part of the number even if the non-haptic notificationindicates otherwise. The non-haptic notification may be visual and/oraudible. A visual notification may include displaying the input ondisplay 123 (e.g., in a text/digit entry field) or, if the input itselfis not displayed, displaying a graphical indication of entry beingaccepted (e.g., a screen flash). Even in examples where the input isdisplayed, since the display is a false indication, the input is notactually used by whatever part of user system 101 receiving input. Forinstance, if user 141 is entering a passcode to enter a bankingapplication, the application would not enter the input as part of thepasscode. Thus, if a person other than user 141 is looking at display123, that person will see the input as being included in the passcodeeven though it is not actually entered. In this example, non-hapticnotification 133 is presented via speaker 122. Non-haptic notification133 may simply indicate that input has been entered implying that theimmediately preceding input element that was described correspond to theinput (e.g., may speak “Input entered”) or non-haptic notification 133may indicate the specific input (e.g., may speak “6 entered” if theinput was for the number 6). If a person overhearing sound made by usersystem 101 hears non-haptic notification 133, that person will hear thatthe input has been entered even though user system 101 has not enteredthe input.

User system 101 may arbitrarily choose when to use haptic notification132 during entry of information from user 141 or may have rules thatdefine when and how often haptic notification 132 should be used. Forexample, a rule governing user system 101 may indicate that, duringentry of information, at least one input per every four charactersentered should be subject of a false non-haptic notification asindicated by an instance of haptic notification 132. Each time usersystem 101 determines that a false non-haptic notification should bepresented, user system 101 repeats steps 202-204. Other input that isnot immediately preceded by an instance of haptic notification 132 isentered. In some examples, user system 101 may automatically detect whensensitive information is being entered (e.g., may recognize a passwordentry field, bank account entry field, etc.) and enable the use ofhaptic notification 132 to indicate false non-haptic notifications. Themethod performed in operation 200 may also be part of a privacy featureof user system 101, or of an application executing on user system 101,that user 141 can instruct user system 101 to turn on to trigger the useof the haptic notifications described herein. In some cases, user 141may be able to turn the feature on/off on the fly whenever they desire(e.g., when sensitive information is to be entered and user 141 is in apublic space, then user 141 may choose to input a button combination,gesture, or other type of input to trigger user system 101 to use thehaptic notifications). User 141 may also be able to define when thehaptic notifications are used (e.g., at all times or for certain typesof information entry). The privacy feature may be a component of anassistive feature (e.g., a component of user system 101 operatingsystem) that visually impaired users use to operate user system 101(e.g., the assistive feature may read out displayed elements and enableuser 141 to select an input that has been read). In other examples,operation 200 may be performed at the direction of the applicationreceiving the input. For instance, a banking application may include afeature that, at least when enabled by user 141 if not on by default,uses instances of haptic notification 132, and corresponding non-hapticnotifications to false indicate input being entered, when user 141 isentering sensitive information into the application.

Advantageously, user system 101 enables user 141 to provide inputs intouser system 101 that are not entered while other inputs are entered.Since user system 101 presents a non-haptic notification that each inputis entered, an eavesdropper on user 141's use of user system 101 cannottell the difference between any of the inputs. Only user 141 knows whichof the inputs was not actually entered due to receiving instances ofhaptic notification 132 prior to certain ones of the inputs.

FIG. 3 illustrates operational scenario 300 for haptically notifying auser that certain input notifications are false. Operational scenario300 is an example where input from two input elements is received byuser system 101. One input to one element is entered and input to theother is not. User system 101 is executing an assistive feature that,when user 141 indicates an input element of graphical input elements 113(e.g., places their finger over the location on display 123 where aparticular input element is displayed), the feature directs user system101 to audibly describe the input element. Even if user 141 is visuallyimpaired, they can determine whether to select the input element forinput based on the audible description thereof. The assistive featuremay also allow user 141 to double tap, or perform some other action, toindicate their desire to select the described input element as input.

In operational scenario 300, display 123 displays graphical inputelements 113 at step 1. In this example, graphical input elements 113are characters that are used to enter a passcode. For example, graphicalinput elements 113 may be keys on a keyboard or number pad displayed onuser system 101. User 141 indicates a first input element of graphicalinput elements 113 at step 2 on display 123. For instance, user 141 mayplace their finger on display 123 and display 123 may detect that thefinger is placed on the first input element. In response, to identifyingthe first input element, speaker 122 presents an audible description ofthe first input element at step 3. For example, if the first inputelement is a key for the letter ‘R’, then speaker 122 may present avoice saying “R” to user 141. User system 101 determines that the nextinput from user 141 should not be entered but, instead, user system 101should present a false non-haptic notification that the input has beenentered. The determination may be made arbitrarily, based on a rule forpresenting false notifications, or based on some other logic. Inresponse to the determination, haptic device 121 presents a hapticnotification (e.g., a vibration pattern) to user 141 at step 4 that thenext input received from user 141 will not be entered. After receivingthe haptic notification, user 141 inputs the first input via display 123at step 5. For instance, since the first input element is the mostrecently described input element of graphical input elements 113, user141 may double tap display 123 to indicate the selection of that input.

In this example, since the first input element is the next input elementafter presenting haptic notification 132, user system 101 ignores theselection of the first input element and does not enter it. Although,user system 101 proceeds with an audible notification at step 7 thatfalsely indicates the first input element was entered. While user 141knows the audible notification is false based on the preceding hapticnotification, anyone overhearing speaker 122 would think that the inputfrom the first input element was entered. If, for example, the firstinput element represented the letter ‘R,’ then speaker 122 may play asound (e.g., a beep) noting that the previously described input wasentered or may play a voice saying the letter ‘R’ was entered eventhough the letter was not entered.

While the haptic notification in this example was played after the firstinput element was described, the haptic notification may be presentedanytime preceding the next input (e.g., may be presented prior to aninput element being described). Similarly, while user 141 chose toselect the first input element in this case, user 141 may have insteadmoved their finger to one or more other input elements of graphicalinput elements 113, and have those elements described via speaker 122,before deciding to select one for false entry. Also, while operationalscenario 300 presents the haptic notification prior to receiving anyinput, it should be understood that user system 101 may allow user 141to provide input using one or more of graphical input elements 113 priorto determining that a false entry notification should be used.

User 141 then indicates a second input element of graphical inputelements 113 on display 123 at step 8. User system 101 audibly describesthe second input element via speaker 122 at step 9 and user 141 selectsthe second input element at step 10. In this case, since a hapticnotification indicating the next input will not be entered was notpresented immediately preceding the selection of the second inputelement, user system 101 enters the selected input of the second inputelement at step 11 and presents an audible notification at step 12 viaspeaker 122 indicating that the input of the second input element hasbeen entered. The audible notification of step 12 is similar to theaudible notification provided at step 7. As such, someone overhearingthe audible notifications would not be able to tell any differencebetween the audible notification that the first input element wasentered and the audible notification that the second input element wasentered. However, user 141 will know that the second input element wasentered while the first input element was not based on the hapticnotification that preceded the audible notification that the first inputelement was entered.

FIG. 4 illustrates operational scenario 400 for haptically notifying auser that certain input notifications are false. Operational scenario400 describes an alternative manner of using haptic device 121 toindicate which inputs are entered by user system 101. Specifically, inthis example, haptic device 121 is used to present haptic notificationsindicating that next input will be entered rather that will not beentered. Operational scenario 400 begins like operational scenario 300with display 123 displaying graphical input elements 113 at step 1.Similarly, user 141 indicates a first input element of graphical inputelements 113 at step 2 and user system 101, responsively, audiblydescribes the first input element at step 3 via speaker 122.

In this example, user system 101 notifies user 141 haptically when thenext input will be entered rather than notifying user 141 when the nextinput will not be entered. User system 101 may use similar logic as inoperational scenario 300 to determine which input should be entered ornot entered but uses a different notification strategy in operationalscenario 400. Specifically, before entering a next input, user system101 presents a haptic notification from haptic device 121 at step 4 tonotify user 141 that the next input will be entered. The hapticnotification comes after speaker 122 presents the description of thefirst input element but could occur at anytime prior to receiving thenext input. After the haptic notification, user 141 selects the firstinput element as input at step 5. Although, in other examples, user 141may indicate other input elements, which are described via speaker 122,prior to finally selecting a next input. In accordance with the hapticnotification provided by user system 101, user system 101 entered theselected input at step 6 and presents an audible notification that theinput has been entered at step 7.

User 141 proceeds with entering information into user system 101 byindicating a second input element at step 8, which is then describedaudibly at step 9 via speaker 122. User 141 selects the second inputelement at step 10. However, since the selection of the second inputelement was not immediately preceded by a haptic alert indicating thenext input selection will be entered, user system 101 ignores theselection and does not enter it at step 11. Despite not entering theselection, user system 101 still presents an audible notification atstep 12 that indicates the selected input was entered in a similarmanner to the audible notification at step 7.

In other examples, the haptic notification mechanisms of operationalscenario 300 and operational scenario 400 may be combined. A hapticnotification of a given type may be presented before every input. Onetype of haptic notification (e.g., one vibration pattern) may bepresented prior to all inputs that will be entered and a different typeof haptic notification (e.g., a different vibration pattern) may bepresented prior to all inputs that will not be entered. For example, asingle vibration pulse may indicate that a next input will be enteredand then a double vibration pulse may indicate that the next input willnot be entered. In both cases, as described herein, a non-hapticnotification will be presented for each input indicating that the inputswere entered.

FIG. 5 illustrates operational scenario 500 for haptically notifying auser that certain input notifications are false. Operational scenario500 is an example of how a visual non-haptic notification may bepresented to user 141. The visual non-haptic notification are describedhere in conjunction with the audible notifications described above inscenarios 300 and/or 400 but may be used independently. Operationalscenario 500 begins with graphical input elements 113 displayed at step1 via display 123. In this example, user 141 again indicates a firstinput element at step 2 and user system 101 responsively describes thefirst input element at step 3 via speaker 122. User system 101determines that the next input will not be entered and presents a hapticnotification from haptic device 121 at step 3 to alert user 141 to thatdetermination. After receiving the haptic notification, user 141 selectsthe first input element at step 5. While this example uses an assistivefeature to audibly describe indicated input elements like the scenariosabove, some examples may not use audible descriptions and associatedinput selection mechanism. For instance, user 141 may not be visuallyimpaired and my simply tap on their desired input element.

Since the haptic notification indicated that the next input receivedfrom user 141 would not be entered, user system 101 ignores theselection for entry purposes at step 6. Despite not entering theselected input, user system 101 still presents both an audiblenotification at step 7 from speaker 122 and a visual notification atstep 8 from display 123 indicating that the selection was entered. Insome examples, the visual notification may include presenting acharacter represented by the first input element in a text entry fielddisplayed by display 123. A person other than user 141 overlookingdisplay 123 would see that the character was entered and believe thatentry actually occurred having not received the haptic notification likeuser 141. User 141, on the other hand, knows the character was notentered despite it being displayed.

FIG. 6 illustrates graphical display 600 of user system 101 forhaptically notifying a user that certain input notifications are false.Graphical display 600 is an example of what may be displayed by display123 when user 141 is entering information into user system 101 withhaptic notifications indicating which inputs are not actually entered.In this example, user 141 is being asked to enter their passcode intoentry field 601. The passcode may be requested to allow user 141 tounlock user system 101, access an application or feature of anapplication on user system 101, access a webpage on user system 101, orfor some other reason a passcode may be required. The passcode in thisexample only includes digits from 0-10 and number pad 602 displays onlythose digits accordingly. The number keys in number pad 602 are anexample of graphical input elements 113 discussed above. Other examplesmay allow other characters for passcode entry and may, therefore,include other graphical input elements (e.g., may display a fullkeyboard layout).

Graphical display 600 shows entry field 601 prior to any inputs beingselected by user 141. In this example, touch point 603 indicates thatuser 141 has placed their finger on the number 6 key of number pad 602.If no assistive feature is activated, then touching the number 6 key mayselect that key. In the above examples where an assistive feature isactivated, user system 101 may provide an audible description of thenumber 6 key so that user 141 knows where their finger is resting. User141 can then perform further action (e.g., double tapping) to select thenumber 6 key. In this example, no haptic notification indicating thenext entry will not be entered is presented to user 141 by user system101 prior to receiving input from the number 6 key. The number 6 is,therefore, entered normally, as shown in graphical display 700.

FIG. 7 illustrates graphical display 700 of user system 101 forhaptically notifying a user that certain input notifications are false.Graphical display 700 is an example of graphical display 600 after user141 has provided six input selections. Entry field 601 now shows thenumber 6, as discussed above with respect to graphical display 600,along with five additional digits. In this example, the passcoderequested from user 141 is only four digits long even though six digitshave been entered. The dots below the ‘2’ and the ‘7’ indicate thatthose two digits were not actually entered by user system 101. That is,immediately prior to user 141 selecting the number 2 key, user system101 presented a haptic notification to user 141 to indicate that thenext input (i.e., the number 2) will not be entered. Similarly, a hapticnotification indicating the next input would not be entered waspresented to user 141 immediately preceding user 141's entry of thenumber 7 key. Although not illustrated, user system 101 may haveprovided an audible confirmation of each digit's entry regardless ofwhether the digit was actually entered, as described in the scenariosabove. Given that the ‘2’ and the ‘7’ were not actually entered forpurposes of recognizing user 141's passcode, the passcode entered byuser 141 is ‘6985’. Presuming that is the correct passcode, user 141will gain access to whatever on user system 101 is requesting thepasscode. A person that sees the display of user system 101 would be ledto believe that the passcode is actually six digits long (i.e., is‘629875’). User 141's actually passcode is, therefore, safe from pryingeyes.

While this example included little dots below the digits that were notentered by user system 101 into user 141's passcode, other examples mayuse different indicators or no indicators at all for those digits. Forinstance, entry field 601 may simply include the string ‘629875’ andrely on user 141 to keep track of which digits were not actuallyentered. Alternatively, indicators may be used to indicate which digitswere actually entered or different indicators may be used todifferentiate digits entered from those that were not. Preferably, ifindicators are to be used, the indicators are such that a personoverlooking user system 101 will not see the indicators or the personwill at least not recognize the indicators as represented whether theinput is actually entered.

FIG. 8 illustrates computing architecture 800 for haptically notifying auser that certain input notifications are false. Computing architecture800 is an example computing architecture for user system 101, althoughuser system 101 may use alternative configurations. Computingarchitecture 800 comprises communication interface 801, user interface802, and processing system 803. Processing system 803 is linked tocommunication interface 801 and user interface 802. Processing system803 includes processing circuitry 805 and memory device 806 that storesoperating software 807.

Communication interface 801 comprises components that communicate overcommunication links, such as network cards, ports, RF transceivers,processing circuitry and software, or some other communication devices.Communication interface 801 may be configured to communicate overmetallic, wireless, or optical links. Communication interface 801 may beconfigured to use TDM, IP, Ethernet, optical networking, wirelessprotocols, communication signaling, or some other communication formatincluding combinations thereof.

User interface 802 comprises components that interact with a user. Userinterface 802 may include a keyboard, display screen, mouse, touch pad,or some other user input/output apparatus. User interface 802 may beomitted in some examples.

Processing circuitry 805 comprises microprocessor and other circuitrythat retrieves and executes operating software 807 from memory device806. Memory device 806 comprises one or more computer readable storagemedia, such as a disk drive, flash drive, data storage circuitry, orsome other memory apparatus including combinations thereof. In noexamples would a computer readable storage medium of memory device 806,or any other computer readable storage medium herein, be considered atransitory form of signal transmission (often referred to as “signalsper se”), such as a propagating electrical or electromagnetic signal orcarrier wave. Operating software 807 comprises computer programs,firmware, or some other form of machine-readable processinginstructions. Operating software 807 comprises computer programs,firmware, or some other form of machine-readable processinginstructions. Operating software 807 includes input privacy module 808.Operating software 807 may further include an operating system,utilities, drivers, network interfaces, applications, or some other typeof software. When executed by processing circuitry 805, operatingsoftware 807 directs processing system 803 to operate computingarchitecture 800 as described herein.

In particular, operating software 807 directs processing system 803 topresent graphical input elements. Input privacy module 808 directsprocessing system 803 to present a haptic notification from the usersystem. The haptic notification indicates that the next input receivedafter presenting the haptic notification will not be entered by the usersystem. In response to receiving input of a first input element of thegraphical input elements immediately following the haptic notification,input privacy module 808 directs processing system 803 to present anon-haptic notification, wherein the non-haptic notification falselyindicates the input has been entered.

The descriptions and figures included herein depict specificimplementations of the claimed invention(s). For the purpose of teachinginventive principles, some conventional aspects have been simplified oromitted. In addition, some variations from these implementations may beappreciated that fall within the scope of the invention. It may also beappreciated that the features described above can be combined in variousways to form multiple implementations. As a result, the invention is notlimited to the specific implementations described above, but only by theclaims and their equivalents.

1. A method comprising: presenting, from a user system, graphical inputelements; presenting a haptic notification from the user system, whereinthe haptic notification indicates that the next input received afterpresenting the haptic notification will not be entered by the usersystem; and in response to receiving input of a first input element ofthe graphical input elements immediately following the hapticnotification, presenting a non-haptic notification, wherein thenon-haptic notification falsely indicates the input has been entered. 2.The method of claim 1, comprising: receiving second input of one of thegraphical input elements; and entering the second input into the usersystem.
 3. The method of claim 2, comprising: presenting a secondnon-haptic notification indicating the second input is entered.
 4. Themethod of claim 2, comprising: before receiving the second input,presenting a second haptic notification that is different from thehaptic notification, wherein the second haptic notification indicatesthat the next input received after presenting the second hapticnotification will be entered by the user system, and wherein the secondinput is received immediately following the second haptic notification.5. The method of claim 2, comprising: after receiving the second input,presenting a second haptic notification that is different from thehaptic notification, wherein the second haptic notification indicatingthe second input is entered.
 6. The method of claim 1, wherein thenon-haptic notification comprises an audible notification.
 7. The methodof claim 1, wherein presenting the graphical input elements comprises:presenting an audible description of the first input element immediatelybefore receiving the input.
 8. The method of claim 1, wherein thenon-haptic notification comprises a visual indication that the input hasbeen entered.
 9. The method of claim 1, wherein the graphical inputelements represent characters for entering a passcode.
 10. The method ofclaim 1, comprising: receiving an instruction from a user of the usersystem activating a privacy feature of the user system, wherein theprivacy feature triggers use of the haptic notification.
 11. Anapparatus comprising: one or more computer readable storage media; aprocessing system operatively coupled with the one or more computerreadable storage media; and program instructions stored on the one ormore computer readable storage media that, when read and executed by theprocessing system, direct the apparatus to: present graphical inputelements; present a haptic notification from the user system, whereinthe haptic notification indicates that the next input received afterpresenting the haptic notification will not be entered by the usersystem; and in response to receiving input of a first input element ofthe graphical input elements immediately following the hapticnotification, present a non-haptic notification, wherein the non-hapticnotification falsely indicates the input has been entered.
 12. Theapparatus of claim 11, wherein the program instructions direct theapparatus to: receive second input of one of the graphical inputelements; and enter the second input into the user system.
 13. Theapparatus of claim 12, wherein the program instructions direct theapparatus to: present a second non-haptic notification indicating thesecond input is entered.
 14. The apparatus of claim 12, wherein theprogram instructions direct the apparatus to: before receiving thesecond input, present a second haptic notification that is differentfrom the haptic notification, wherein the second haptic notificationindicates that the next input received after presenting the secondhaptic notification will be entered by the user system, and wherein thesecond input is received immediately following the second hapticnotification.
 15. The apparatus of claim 12, wherein the programinstructions direct the apparatus to: after receiving the second input,present a second haptic notification that is different from the hapticnotification, wherein the second haptic notification indicating thesecond input is entered.
 16. The apparatus of claim 11, wherein thenon-haptic notification comprises an audible notification.
 17. Theapparatus of claim 11, wherein to present the graphical input elements,the program instructions direct the apparatus to: present an audibledescription of the first input element immediately before receiving theinput.
 18. The apparatus of claim 11, wherein the non-hapticnotification comprises a visual indication that the input has beenentered.
 19. The apparatus of claim 11, wherein the program instructionsdirect the apparatus to: receiving an instruction from a user of theuser system activating a privacy feature of the user system, wherein theprivacy feature triggers use of the haptic notification.
 20. One or morecomputer readable storage media having program instructions storedthereon that, when read and executed by a processing system, direct theprocessing system to: present graphical input elements; present a hapticnotification, wherein the haptic notification indicates that the nextinput received after presenting the haptic notification will not beentered by a user system; and in response to receiving input of a firstinput element of the graphical input elements immediately following thehaptic notification, present a non-haptic notification, wherein thenon-haptic notification falsely indicates the input has been entered.